Workbench Design/WB Collection.iso/workbench werkzeuge/uhren & terminkalender/time/barclock/barclock.guide

Amigaguide Document | 1996-04-07 | 5KB | 119 lines

@DATABASE "BarClock.guide"
@$VER: BarClock v2.2 (1994)
@NODE Main "BarClock - Contents"
               @{b}BarClock v2.2@{ub}
 1994 Stephen Davies - Freely distributable
              @{" INTRODUCTION " link node_int}
              @{" USAGE        " link node_use}
              @{" NOTES        " link node_notes}
              @{" WARNING      " link node_bugs}
              @{" HISTORY      " link node_hist}
              @{" CREDITS      " link node_cre}
@ENDNODE
@NODE node_int "BarClock - Introduction"
 @{b}What is it?@{ub}
   BarClock is, I'm afraid, yet another clock program.
   This program displays the time in screen/window title bars.
 @{b}Features@{ub}
   Use standard AmigaDOS wildcards to specify screens
   Can display date as well as time
   Can display in windows if screen's title bar is obscured
   Supports proportional fonts
@ENDNODE
@NODE node_use "BarClock - Usage"
 @{b}Launching BarClock@{ub}
   BarClock can be run from the CLI or from Workbench. It requires
   no assigns, special libraries, etc. but does require WB 2.0+
   To have BarClock running every time you boot-up, drag its icon
   into WBStartUp or add "run >NIL: BarClock" to S:User-StartUp and
   ensure BarClock is in your path.
 @{b}Arguments@{ub}
   CLI args:      "S=SCREENS/K,DS=DATE_SCREENS/K,WS=WIN_SCREENS/K,QUIT/S"
   WB ToolTypes:  "SCREENS=<pattern>",
                  "DATE_SCREENS=<pattern>",
                  "WIN_SCREENS=<pattern>"
   where...
     SCREENS:      BarClock will be displayed only on screens
                   whose default title matches this pattern.
     DATE_SCREENS: Display date as well as time on any screen
                   whose default title matches this pattern.
     WIN_SCREENS:  Display in windows which obscure the screen title bar
                   of any screen whose default title matches this pattern.
     QUIT:         Quit BarClock if it is running.
   Note: The default title of a @{i}public@{ui} screen can be different to its name.
 @{b}Exiting BarClock@{ub}
   Either...
     launch it again from the WB
   or...
     launch from the CLI with QUIT argument
   or...
     send it a Break (Ctrl C) signal (if started from CLI)
@ENDNODE
@NODE node_notes "BarClock - Notes"
 @{b}BarClock description@{ub}
   BarClock displays the time on the frontmost screen which matches
   the SCREENS argument. If the screen also matches DATE_SCREENS, the
   date will also be displayed.
   On a screen which matches WIN_SCREENS, if the screen title bar is
   obscured by a window, and the clock will fit on that window, then
   the clock is drawn in that window instead.
   If two windows are blocking the screen title bar then BarClock will
   draw on the frontmost window that is wide enough. It may be the case
   that there is a "higher" window blocking BarClock's window yet not
   blocking the screen title bar, but I could not be bothered to check
   for this.
 @{b}Amiga screens@{ub}
   For those who don't know, I'll just explain a bit about screens
   on the Amiga. Seasoned Amiga users should know all this...
   If you look at the title bar of the Workbench screen, you will see
   it says different thing when different applications's windows are
   active. However, screens also have a default title which should
   never change.
   The default title is displayed when no window on that screen is
   active or when an application doesn't bother supplying a screen
   title. It is the default title which BarClock compares against the
   user supplied arguments.
   Note: the default title of a @{i}public@{ui} screen may not be the same as
   the screen's name. For example, the Workbench screen has a default
   title of "Workbench Screen" but a name of "Workbench".
@ENDNODE
@NODE node_bugs "BarClock - Warning"
 @{b}Warning@{ub}
   Rendering into other application's windows/screens is naughty.
   Having said that, it does have some advantages (especially for a
   lazy programmer) so that's the way I have chosen to go.
   I've taken every precaution I could think of to ensure BarClock
   causes as little disruption as possible to other tasks, and have
   been running it for over a year without any problems.
 @{b}Disclaimer@{ub}
   I will accept no liability for any loss, damage, injury, death,
   etc., arising directly or indirectly from the use of BarClock.
@ENDNODE
@NODE node_hist "BarClock - History"
 @{b}Versions 1.0 to 1.7@{ub}
   Not released
 @{b}Version 2.0@{ub}
   First release
 @{b}Version 2.1@{ub}
   No longer renders in windows that are too narrow
   Ignores BACKDROP windows if SHOWTITLE is set
 @{b}Version 2.2@{ub}
   Won't render over window CLOSE (or other non-RELRIGHT) gadgets
   Enforcer hits removed
@ENDNODE
@NODE node_cre "BarClock - Credits"
 @{b}Amiga set-up@{ub}
   A1200 with 170Mb HD, 2+4Mb RAM and 1942 monitor.
 @{b}Author@{ub}
   Stephen Davies
   98 Larches Lane
   Ashton
   Preston
   Lancs
   England
   PR2 1PP
   Fido: 2:2500/73.18
 @{b}Thanks to@{ub}
   Mike Dodd for finding the Enforcer hits.
@ENDNODE